End of life prediction of flash memory

ABSTRACT

Disclosed are a method, electronic device, and computer readable medium for determining an end-of-life stage of the flash memory. The method includes detecting at least one life cycle event associated with a flash memory residing on an electronic device. A counter that is associated with the life cycle event is then incremented. Based on the counter, a total number of occurrences for the one life cycle event is determined. The total number of occurrences for the at least one given threshold is also determined. A current life cycle stage of the flash memory is identified based at least in part on determining if the total number of occurrences exceeds at least one given threshold. The life cycle stage is associated with the at least one given threshold. A user is then notified of the life cycle state of the flash memory.

FIELD OF THE INVENTION

The present invention generally relates to the field of memory devices,and more particularly relates to end of life prediction for flashmemory.

BACKGROUND OF THE INVENTION

Flash memory provides non-volatile memory where blocks (which includemultiple locations) of flash memory are erasable in a flash operation.Flash memory comprises cells, which are an array of floating gatetransistors, for storing information. Traditionally one bit ofinformation can be stored in each cell. However, some flash memorydevices such as multi-cell memory devices can store more than one bitper cell. Two well-known types of circuitry that are present in flashmemory cells are NAND and NOR.

Flash memory is currently limited by the fact that it has a finitenumber of erase-write cycles. Current flash memory does not have a wayto notify a user of its erase-write cycle life is being approached orhas been exceeded. In other words, users are not able to predict whentheir flash memory devices are about to fail. When a flash memory devicefails, the device is inoperable and any data stored on the device islost or corrupted. Without being informed of a possible device failure,a user may continue to store critical information on the flash memory,which will be lost when the flash memory device fails.

Therefore a need exists to overcome the problems with the prior art asdiscussed above.

SUMMARY OF THE INVENTION

Briefly, in accordance with the present invention, disclosed are amethod, electronic device, and computer readable medium for determiningan end-of-life stage of the flash memory. The method comprises detectingat least one life cycle event associated with a flash memory residing onan electronic device. A counter that is associated with the life cycleevent is then incremented. Based on the counter, a total number ofoccurrences for the one life cycle event is determined. The total numberof occurrences for the at least one given threshold are also determined.The total number of occurrences for the at least one life cycle eventare stored on the flash memory. The method also includes determiningwhether the total number of occurrences exceeds at least one giventhreshold. A current life cycle stage of the flash memory is identifiedbased at least in part on the determining if the total number ofoccurrences exceeds at least one given threshold. The life cycle stageis associated with the at least one given threshold. A user is thennotified of the life cycle state of the flash memory.

In another embodiment, a method with a first electronic devicecommunicatively coupled to at least a second electronic device includingat least one flash memory, for determining an end-of-life stage of theflash memory is disclosed. The method comprise detecting, by the firstelectronic device at least one life cycle event associated with a flashmemory residing on the at least second electronic device. The firstelectronic device is communicatively to the at least second electronicdevice. A counter associated with the life cycle event is thenincremented. Based on the counter, a total number of occurrences for theone life cycle event is determined. The total number of occurrences forthe at least one life cycle event is stored on the flash memory. Themethod also includes determining whether the total number of occurrencesexceeds at least one given threshold. A current life cycle stage of theflash memory is identified based at least in part on the determining ifthe total wherein The life cycle stage is associated with the at leastone given threshold. A user is then notified of the life cycle state ofthe flash memory.

In yet another embodiment, an electronic device comprising at one flashmemory module is disclosed. The electronic device includes at least oneflash memory module and a life cycle event counter communicativelycoupled to the at least one flash memory. The life cycle counter detectsat least one life cycle event associated with the at least one flashmemory module. The life cycle counter increments a life cycle count forthe at least one life cycle event. The life cycle count is stored on theat least one flash memory module. The electronic device also includes alife cycle stage estimator that is communicatively coupled to the lifecycle counter and the at least one flash memory module. The life cyclestage estimator determines a total number of occurrences for the atleast one life cycle event.

The life cycle stage estimator also determines if the total number ofoccurrences exceeds at least one given threshold. The life cycle stageestimator identifies a current life cycle stage of the flash memorybased at least in part on the determining if the total number ofoccurrences exceeds at least one given threshold. The life cycle stageis associated with the at least one given threshold. At least onenotification module is also included in the electronic device. The atleast one notification module notifies a user of the life cycle state ofthe flash memory module.

In another embodiment, a computer readable medium for determining anend-of-life stage of the flash memory is disclosed. The computerreadable medium comprises instructions for detecting at least one lifecycle event associated with a flash memory residing on an electronicdevice. A counter that is associated with the life cycle event is thenincremented. Based on the counter, a total number of occurrences for theone life cycle event is determined. The total number of occurrences forthe at least one given threshold are also determined. The total numberof occurrences for the at least one life cycle event are stored on theflash memory. The method also includes determining whether the totalnumber of occurrences exceeds at least one given threshold. A currentlife cycle stage of the flash memory is identified based at least inpart on the determining if the total number of occurrences exceeds atleast one given threshold. The life cycle stage is associated with theat least one given threshold. A user is then notified of the life cyclestate of the flash memory.

In a further embodiment, a computer readable medium on a firstelectronic device communicatively coupled to at least a secondelectronic device including at least one flash memory, for determiningan end-of-life stage of the flash memory is disclosed. The computerreadable medium comprising instructions for determining an end-of-lifestage of the flash memory is disclosed. The method comprise detecting,by the first electronic device at least one life cycle event associatedwith a flash memory residing on the at least second electronic device.The first electronic device is communicatively to the at least secondelectronic device. A counter associated with the life cycle event isthen incremented. Based on the counter, a total number of occurrencesfor the one life cycle event is determined. The total number ofoccurrences for the at least one life cycle event is stored on the flashmemory. The method also includes determining whether the total number ofoccurrences exceeds at least one given threshold. A current life cyclestage of the flash memory is identified based at least in part on thedetermining if the total wherein The life cycle stage is associated withthe at least one given threshold. A user is then notified of the lifecycle state of the flash memory.

One advantage of the present invention is that a user is notified when aflash memory device is reaching its end-of-life cycle. The device itselfcan include a notification means such as LED lights, an audiblenotification, and the like so that a user can be notified by the devicewhen it is reaching its end-of-life cycle. Additionally, the end-of-lifecycle of a flash memory can be monitored by another device such as acomputer system housing the flash memory. Physical hardware and/orsoftware on the external device can monitor the flash memory so that auser can be notified when the flash memory's end-of-life cycle isapproaching or has been exceeded. Accordingly, a user can transfercritical data off of the flash memory prior to the memory failing.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying figures where like reference numerals refer toidentical or functionally similar elements throughout the separateviews, and which together with the detailed description below areincorporated in and form part of the specification, serve to furtherillustrate various embodiments and to explain various principles andadvantages all in accordance with the present invention, in which:

FIG. 1 is a block diagram illustrating an exemplary flash memoryaccording to an embodiment of the present invention;

FIG. 2 is block diagram illustrating an exemplary information processingsystem according to an embodiment of the present invention;

FIG. 3 is a block diagram illustrating one example of notifying a userof a current life cycle stage for a flash memory according to anembodiment of the present invention;

FIG. 4 and FIG. 5 are block diagrams illustrating a flash memory deviceindicating to a user its current end-of-life state according to anembodiment of the present invention; and

FIG. 6 is an operational flow diagram illustrating an exemplary processof determining a current life-cycle stage of a flash memory according toan embodiment of the present invention.

DETAILED DESCRIPTION

The present invention as would be known to one of ordinary skill in theart could be produced in hardware or software, or in a combination ofhardware and software. However in one embodiment the invention isimplemented in software. The system, or method, according to theinventive principles as disclosed in connection with the preferredembodiment, may be produced in a single computer system having separateelements or means for performing the individual functions or stepsdescribed or claimed or one or more elements or means combining theperformance of any of the functions or steps disclosed or claimed, ormay be arranged in a distributed computer system, interconnected by anysuitable means as would be known by one of ordinary skill in the art.

According to the inventive principles as disclosed in connection withthe preferred embodiment, the invention and the inventive principles arenot limited to any particular kind of computer system but may be usedwith any general purpose computer, as would be known to one of ordinaryskill in the art, arranged to perform the functions described and themethod steps described. The operations of such a computer, as describedabove, may be according to a computer program contained on a medium foruse in the operation or control of the computer, as would be known toone of ordinary skill in the art. The computer medium, which may be usedto hold or contain the computer program product, may be a fixture of thecomputer such as an embedded memory or may be on a transportable mediumsuch as a disk, as would be known to one of ordinary skill in the art.

The invention is not limited to any particular computer program or logicor language, or instruction but may be practiced with any such suitableprogram, logic or language, or instructions as would be known to one ofordinary skill in the art. Without limiting the principles of thedisclosed invention any such computing system can include, inter alia,at least a computer readable medium allowing a computer to read data,instructions, messages or message packets, and other computer readableinformation from the computer readable medium. The computer readablemedium may include non-volatile memory, such as ROM, Flash memory,floppy disk, Disk drive memory, CD-ROM, and other permanent storage.Additionally, a computer readable medium may include, for example,volatile storage such as RAM, buffers, cache memory, and networkcircuits. Furthermore, the computer readable medium may include computerreadable information in a transitory state medium such as a network linkand/or a network interface, including a wired network or a wirelessnetwork that allows a computer to read such computer readableinformation.

Exemplary Flash Memory Device

FIG. 1 is a block diagram of an exemplary flash memory device 100according to an embodiment of the present invention. In one embodimentof the present invention, the flash memory device 100 is an externaldevice such as a Universal Serial Bus (“USB”) flash device. However, itshould be noted that the present invention is not limited to externalflash memory devices or flash memory devices utilizing a USBcommunication interface. For example, the present invention is alsoapplicable to internal flash memory found in many devices such aswireless communication devices, service processors, desktop computers,notebook computers, and the like.

In one embodiment, the flash memory device 100 includes a communicationinterface 102 such as a USB interface. The communication interface 102allows the flash memory device 100 to communication with another devicesuch as a desktop or notebook computer. The flash memory device 100 alsoincludes an array of non-volatile flash memory cells 104. In oneembodiment, the memory cells are arranged in a plurality of addressablebanks. The data stored in the memory 104 can be accessed usingexternally provided addresses. A controller 106 is also included in theflash memory device 100 for controlling read/write cycles of the flashmemory device, user notifications (via the notification interface 110),and the like. The notification interface 110 can include one or morelight emitting diodes (“LED”) or their equivalent, a speaker for audiblealerts, and the like. The notification interface 110 can notify the userof a power on/off cycle, read/write cycle, and/or end-of-life status ofthe flash memory device 100.

In one embodiment, the controller 106 includes one or more counters 108,which monitor the read/write cycles, power cycles, and the like of theflash memory device 110. In one embodiment, a single counter 108 can beused to monitor relevant activities or an individual counter can be usedto monitor each of read cycles, write cycles, power cycles, and thelike. The activities can be monitored in real time (i.e. as they happen)or the number of occurred activities can be counted each time the flashmemory device 100 is “plugged in” to an external device such as aninformation processing system. In one embodiment, the counter 108 storesthe event count (number of writes, reads, power cycles, errors, and thelike) on in the flash memory cells 104.

The controller 108 can also include additional optional counters 114. Inone embodiment, one or more counters 114 or not integrated with theflash memory device 100. For example, when the flash memory device 100is communicatively coupled (e.g., plugged into) an external device suchas an information processing system, the operating system of theinformation processing system saves the non-integrated counter 114 toits hard drive or other storage medium. Therefore the counter 114 isportable and the information processing system can read the counter fromits storage medium. It should be noted that the non-integrated counter114 can reside outside of the controller. An end-of-life predictionmodule 112 uses the information monitored by the counter(s) 108 todetermine a status of the flash memory device 100 with respect to itsend-of-life period. An end-of-life period is the point of completefailure by the flash memory device when its limit of read/write cycleshas occurred.

The controller 106, in one embodiment, can also analyze the counter(s)108 for detecting counter malfunctions and/or defective counters. Forexample, the controller 106 analyzes the counter(s) 108 to identify thecounter(s) 108 has decreasing counts or numbers going past a setthreshold. In response to detecting a malfunctioning counter 108 or adefective counter 108, the controller 108 can change the life cyclestage for notifying a user of the detected problem.

In one embodiment, the end-of-life prediction module 112 includesvarious weighting logic to assign weights to each of the activitiesmonitored by the one or more counters 108. For example, writes to memorycells 104 or more intensive than reads to memory cells 104, therebyconsuming more of the memory device's lifespan. Therefore, in oneembodiment, each of the monitored can have a different weight assignedto them. The end-of-life prediction module 112, in one embodiment, usesthese weights, the number of instances monitored for each activity, andthe known end-of-life time period to determine the current life cyclestage of the flash memory device 100.

In one embodiment, the end-of-life prediction module 112 estimates whenthe flash memory device 100 is going to fail based on the componentsdetected within the device. In another embodiment, a manufacturer canpre-program the number of read/write cycles, power on cycles, errorsthat can occur before the device fails. The counter(s) 108, in oneembodiment, can count the number of errors present in each memory cell104. The end-of-life prediction module 112 can then use the number oferrors detected as a further indicator of the flash memory device's 100current life cycle stage.

In this example, the counter 108 can be incremented by a heavy weightingfactor (e.g. giving more weight to an erroneous count) that can beincreased as the number of errors increases. This can be based onintrinsic failure information of the flash memory device 100 given bythe manufacturer, usage experience in testing or customer installations,and the like. One advantage of detecting errors is the ability to havean early detection of possible failure by the flash memory device 100.It should be noted that, in one embodiment, the end-of-life predictionmodule 112 can reside within the counter(s) 108.

Once the end-of-life prediction module 112 determines the life cyclestage of the flash memory device 100, it can display the life cyclestatus to the user. For example, the notification interface 110 candisplay a visual notification such as a blinking light, colored lights,or a combination thereof to indicate a particular state in the lifecycle of the flash memory device 100. Alternatively, an audiblenotification such as a beep or a combination of beeps can also be used(or in conjunction with a visual notification) to indicate to a user thelife cycle stage of the flash memory device 100. The life cycle stagenotification process is discussed in greater detail below.

In one embodiment, the counter(s) 108 and/or the end-of-life predictionmodule 112 are accessible via one or more addresses by an externalprocessing interface such as an information processing machine. Theexternal device can perform further validation of the life cycle stageof the flash memory device 100 and/or inform the user the life cyclestage of the flash memory device 100. When an external processinginterface is used the counter 108 can be read once or at variousintervals. Historical information associated with the device such asread/write cycles, power-on cycles, ad the like can then be recorded. Inthis example, the information processing device can provide usagestatistics, or more advanced analysis on when a failure might occur. Theinformation processing device can then communicate with other componentsto start a service process for replacing the flash memory.

In this example, an electronic service call can be generated and aservice technician can be dispatched to follow a service procedure toreplace that particular part. An example of this system is a System pModel p595 commercially available from the International BusinessMachines Corporation (IBM) of White Plains, N.Y., United States ofAmerica. In this example the hardware management console (“HMC”) canread the counters (108) from redundant service processors that utilizeflash memory as their storage mechanism. The counters 108 are read todetermine if the service processor which includes the flash memory needsto be replaced. Once the HMC determines if the flash memory needs to bereplaced it can generate a service event with IBM service focal pointthat orders the part, notifies the customer, and places a service callto have the part replaced.

Exemplary Information Processing System

FIG. 2 is a block diagram illustrating a detailed view of an informationprocessing system 200. The information processing system 200 is basedupon a suitably configured processing system adapted to implement theexemplary embodiment of the present invention. Any suitably configuredprocessing system is similarly able to be used as the informationprocessing system 200 by embodiments of the present invention, forexample, a personal computer, workstation, wireless communicationdevice, gaming counsel, hand-held gaming device, or the like.

The information processing system 200 includes a computer 202. Thecomputer 202 has a processor 204 that is connected to the main memory206, flash memory 208, mass storage interface 210, terminal interface212, and a network adapter hardware 214 via a system bus 216. The massstorage interface 210 is used to connect mass storage devices such asdata storage device 216 to the information processing system 200. Onespecific type of data storage device is a computer readable medium suchas a CD drive, which may be used to store data to and read data from aCD 218 or its equivalent. Another type of data storage device is a datastorage device configured to support, for example, NTFS type file systemoperations.

The main memory 206, in one embodiment, can be volatile memory such asRandom Access Memory (“RAM”) includes, among other things, a counter220, an end-of-life prediction module 222, and an end-of-life cyclenotification interface 224. It should be noted that one or more of thesecomponents can reside within the flash memory 208 instead of the mainmemory 206. The counter 220, similar to the counter 108 discussed abovein FIG. 1, monitors the read/write cycles, power cycles, and the like ofthe flash memory 208. In one embodiment, a single counter 220 monitorsthe relevant activities or individual counters can be used to monitoreach of the read cycles, the write cycles, the power cycles, errors andthe like.

The counter 220 can be monitor and count these activities in real timeor can be counted at various given time intervals such as the startup ofthe information processing system 200. The end-of-life prediction module222, similar to the end-of-life prediction module 112, uses the countedinformation to determine the current life cycle stage of the flashmemory 208. The counter 220, in one embodiment, can also be thenon-integrated counter 114 discussed above. In other words the counter220 can be retrieved from the flash memory device 100 and stored inmemory 206. Also, more than one counter 220 can be included in theinformation processing system 200.

The end-of-life prediction module 112, or the counter 220 itself, canassign weights to each of the monitored/counted activities as discussedabove. The end-of-life prediction module 222, in one embodiment, usesthese weights, the number of instances monitored/counted for eachactivity, and the known end-of-life time period to determine the currentlife cycle stage of the flash memory device 100. It should be noted thatweights do not have to be assigned to the monitored/counted activities.

As discussed above, the end-of-life prediction module 222 can estimate agiven end-of-life period of the flash memory 208 based on the componentsdetected within the flash memory 208. In another embodiment, amanufacture can pre-program the number of read/write cycles, power oncycles, errors that can occur before the flash memory 308 fails. Thenumber of errors in the flash memory 208, as discussed above, can alsobe counted by the counter 220 for use as a further indicator of theflash memory's current life cycle stage.

Once the end-of-life prediction module 222 determines the life cyclestage of the flash memory 208, the user can be notified. For example,the end-of-life notification interface 224 can use a visual and/or anaudible notification to inform the user of the flash memory's 208current life cycle stage. For example, if the counter 220 andend-of-life prediction module 222 are implemented as software, acorresponding software program can visually and/or audibly notify a userof the current life cycle stage of the flash memory 208. A visualnotification can be a pop-up message on a display, a new window beingdisplayed to a user, a blinking widget, a newly displayed widget, anemail, and the like.

For example, FIG. 3 shows a display 300 comprising a user interface 302and a window 304. The window 304 includes various messages that can bedisplayed to a user regarding the life cycle stage of the flash memory208. For example, a first message 306 indicates that the life-cycle ofthe flash memory 208 is above average and has a certain percentageremaining. A second message 308 indicates that the life-cycle of theflash memory 208 is average and has a certain percentage remaining. Athird message 310 indicates that the life cycle is critical and memoryfailure is going to occur soon. A fourth message 312 indicates that acounter mismatch has occurred. For example, if the counter 220 on theinformation processing system 200 is greater than the counter on theflash memory device 100, the user is notified.

It should be noted that the present invention is not limited to any oneway of visually notifying the user of the current life cycle stage ofthe flash memory 208. It should also be noted that these methods forvisually notifying a user can also be implemented in the embodimentwhere a flash memory device 100 is connected to the informationprocessing system 200, which determines the life-cycle stage of theflash memory device 100.

Although illustrated as concurrently resident in the main memory 206 itis clear that respective components of the main memory 306 are notrequired to be completely resident in the main memory 206 at all timesor even at the same time. In one embodiment, the information processingsystem 200 utilizes conventional virtual addressing mechanisms to allowprograms to behave as if they have access to a large, single storageentity, referred to herein as a computer system memory, instead ofaccess to multiple, smaller storage entities such as the main memory 206and data storage device 216. Note that the term “computer system memory”is used herein to generically refer to the entire virtual memory of theinformation processing system 200.

Although only one CPU 204 is illustrated for computer 202 computersystems with multiple CPUs can be used equally effectively. Embodimentsof the present invention further incorporate interfaces that eachincludes separate, fully programmed microprocessors that are used tooff-load processing from the CPU 204. Terminal interface 212 is used todirectly connect one or more terminals 226 to computer 202 to provide auser interface to the computer 202. These terminals 226, which are ableto be non-intelligent or fully programmable workstations, are used toallow system administrators and users to communicate with theinformation processing system 200. The terminal 212 is also able toconsist of user interface and peripheral devices that are connected tocomputer 202 and controlled by terminal interface hardware included inthe terminal I/F 212 that includes video adapters and interfaces forkeyboards, pointing devices, and the like.

An operating system (not shown) included in the main memory 206 is asuitable multitasking operating system such as the Linux, UNIX, WindowsXP, and Windows Server 2003 operating system. Embodiments of the presentinvention are able to use any other suitable operating system. Someembodiments of the present invention utilize architectures, such as anobject oriented framework mechanism, that allows instructions of thecomponents of operating system (not shown) to be executed on anyprocessor located within the information processing system 200. Thenetwork adapter hardware 214 is used to provide an interface to anetwork such as a wireless network, WLAN, LAN, or the like (not shown).Embodiments of the present invention are able to be adapted to work withany data communications connections including present day analog and/ordigital techniques or via a future networking mechanism.

Although the exemplary embodiments of the present invention aredescribed in the context of a fully functional computer system, thoseskilled in the art will appreciate that embodiments are capable of beingdistributed as a program product via a CD/DVD, e.g. CD 218, or otherform of recordable media, or via any type of electronic transmissionmechanism.

Example of Visually Notifying a User of a Current Life-Cycle Stage

FIG. 4 and FIG. 5 are block diagrams illustrating one example ofvisually notifying a user of a current life cycle stage of the flashmemory device 100 of FIG. 1. The known end-of-life cycle for theexemplary flash memory device 100 is assumed to be 100 for the examplesof FIG. 4 and FIG. 5. As discussed above, the actual end-of-life cyclecan be determined based on the components in the flash memory device 100or by a number pre-programmed in by the manufacturer.

In one embodiment, based on the number of read/write cycles, powercycles, errors, and the like, the end-of-life prediction module 112 orthe counter 108 sends a signal to the notification interface 110. Inthis example, the LED lights 402, 404, 406 already existing on the flashmemory device 100 are used to indicate the current life cycle of theflash memory device 100. For example, if between 0 and 50 life cycles(which can include any one of or an aggregation of read/write cycles,power cycles, errors, and the like) have occurred, a specific LED(s) orpattern of LEDs can be turned on. For example, FIG. 4 shows that a firstLED 402 is displayed.

If between 50 and 75 life cycles have occurred, a second set of LED(s)or pattern of LEDs can be displayed. FIG. 4 shows that no LEDs aredisplayed to indicate that the current life cycle is at an intermediatestate of between 50 and 75 life cycles. FIG. 4 also shows a thirdexample for indicating to a user that the flash memory device 100 is ata critical life cycle stage. For example, FIG. 4 shows that a third LED406 is displayed for notifying the user that at least 75 out of the 100available life cycles of the flash memory device 100 have occurred. If adevice only has a single LED available, as shown in FIG. 5, the singleLED 502 can be steadily displayed (constantly lit), not displayed,intermittently blinking, steadily blinking, blinking in variouspatterns, and the like. For example, an indication of between 0 and 50life cycles having occurred can result in the LED 502 being constantlydisplayed. An indication of between 50 and 75 life cycles havingoccurred can result in the LED not being displayed. An indication of atleast 75 life cycles occurring can result in the LED 502 blinkingrapidly.

It should be noted that the examples in FIG. 4 and FIG. 5 areillustrative and not limiting. Any combination or LEDs, colors, blinkingpatterns may be used to indicate a current life cycle state of the flashmemory device 100. Also, as discussed above, an audile notification canalso be used in place or in combination with the visual notification.Furthermore, in flash memory devices comprising a display screen such asportable MP3 players (and the like), the visual notification cancomprise of text and/or symbols.

Exemplary Process of Determining a Current Life Cycle Stage for a FlashMemory (Device)

FIG. 6 shows an exemplary process of determining a current life cyclestage for a flash memory (device). The operational flow diagram of FIG.6 begins at step 602 and flows directly to step 602. The followingdiscussion is applicable to a flash memory device such as the device 100in FIG. 1 or to an internal flash memory 208 as shown in FIG. 2. Acounter 108, 220, at step 604, monitors a flash memory 104, 208 for lifecycle events such as read/write cycles, power cycles, errors, and thelike. The counter 108, 220, at step 606, determines if a life cycleevent has occurred. If the result of this determination is negative, thecontrol flows back to step 604 where the counter 108, 220 continues tomonitor. If the result of this determination is positive, the counter108, 220, at step 608, increases the current count for that particularlife cycle event.

The counter 108, 200 or the end-of-life prediction module 112, 222, atstep 610, optionally assigns a weight to the life cycle event. Asdiscussed above, one life cycle even such as a write can weigh moreheavily than another life cycle event such as a read. Based on thecounted life cycle events, the end-of-life prediction module 112, 222,at step 612, determines a current life cycle stage for the flash memory104, 208. The user, at step 614, is notified of the current life cycleevent of the flash memory 104, 208. For example, a visual notification(as discussed with respect to FIGS. 3-5) or an audible notification canindicate to a user the current life cycle stage of the flash memory 104,208. The control flow then exits at step 616.

It should be noted that the above process can be performed eitherdirectly on a flash memory device 100, an information processing systemcomprising flash memory 208, or by an information processing systemcommunicatively coupled to an external flash memory device 100.

Non-Limiting Examples

The present invention can be realized in hardware, software, or acombination of hardware and software. A system according to a preferredembodiment of the present invention can be realized in a centralizedfashion in one computer system or in a distributed fashion wheredifferent elements are spread across several interconnected computersystems. Any kind of computer system—or other apparatus adapted forcarrying out the methods described herein—is suited. A typicalcombination of hardware and software could be a general purpose computersystem with a computer program that, when being loaded and executed,controls the computer system such that it carries out the methodsdescribed herein.

In general, the routines executed to implement the embodiments of thepresent invention, whether implemented as part of an operating system ora specific application, component, program, module, object or sequenceof instructions may be referred to herein as a “program.” The computerprogram typically is comprised of a multitude of instructions that willbe translated by the native computer into a machine-readable format andhence executable instructions. Also, programs are comprised of variablesand data structures that either reside locally to the program or arefound in memory or on storage devices. In addition, various programsdescribed herein may be identified based upon the application for whichthey are implemented in a specific embodiment of the invention. However,it should be appreciated that any particular program nomenclature thatfollows is used merely for convenience, and thus the invention shouldnot be limited to use solely in any specific application identifiedand/or implied by such nomenclature.

Although specific embodiments of the invention have been disclosed,those having ordinary skill in the art will understand that changes canbe made to the specific embodiments without departing from the spiritand scope of the invention. The scope of the invention is not to berestricted, therefore, to the specific embodiments, and it is intendedthat the appended claims cover any and all such applications,modifications, and embodiments within the scope of the presentinvention.

1. A method, with an electronic device, for determining an end-of-lifestage of the flash memory, the method comprising: detecting at least onelife cycle event associated with a flash memory residing on anelectronic device; assigning one of a plurality of weights to the atleast one life cycle event based on a life cycle event type associatedwith the at least one life cycle event; incrementing a counterassociated with the at least one life cycle event based on the weightthat has been assigned to the at least one life cycle event;determining, based on the counter, a total number of occurrences for theat least one life cycle event; storing the total number of occurrencesfor the at least one life cycle event on the flash memory; determiningif the total number of occurrences exceeds at least one given threshold;identifying a current life cycle stage of the flash memory based atleast in part on the determining if the total number of occurrencesexceeds at least one given threshold, wherein the life cycle stage isassociated with the at least one given threshold; and notifying a userof the life cycle state of the flash memory.
 2. The method of claim 1,wherein the at least one life cycle event comprises at least one of: awrite cycle to the flash memory; a read cycle from the flash memory; apower on cycle of the device comprising the flash memory; and an errorexisting in a memory cell of the flash memory.
 3. The method of claim 1,wherein the identifying is based at least in part on the determining ifthe total number of occurrences exceeds at least one given threshold andthe weight assigned to the at least one life cycle.
 4. The method ofclaim 1, wherein the notifying further comprises at least one of:visually notifying the user; and audibly notifying the user.
 5. Themethod of claim 4, wherein the visually notifying further comprises atleast one of: illuminating, at least once, a set of visual indicatingmeans on the device; displaying text on a display of the device; andgraphically illustrating on an external display communicatively coupledto the device, a visual notification associated with the current lifecycle stage.
 6. The method of claim 1, wherein the current life cyclestage includes at least one of: a percentage of an estimated life timeremaining for the flash memory; an estimated number of remaining lifecycle events available for the flash memory; and an indication of theestimated life time remaining for the flash memory being one of: aboveaverage, average, and critical.
 7. The method of claim 1, wherein thedetecting is performed by the device comprising the flash memory.
 8. Themethod of claim 1, wherein the detecting is performed by anotherelectronic device communicatively coupled to the electronic device.
 9. Amethod, with a first electronic device communicatively coupled to atleast a second electronic device including at least one flash memory,for determining an end-of-life stage of the flash memory, the methodcomprising: detecting, by a first electronic device communicativelycoupled to at least a second electronic device, at least one life cycleevent associated with a flash memory residing on the at least secondelectronic device; assigning one of a plurality of weights to the atleast one life cycle event based on a life cycle event type associatedwith the at least one life cycle event; incrementing a counterassociated with the life cycle event based on the weight that has beenassigned to the at least one life cycle event; determining, based on thecounter, a total number of occurrences for the at least one life cycleevent; storing the total number of occurrences for the at least one lifecycle event on the flash memory; determining if the total number ofoccurrences exceeds at least one given threshold; identifying a currentlife cycle stage of the flash memory based at least in part on thedetermining if the total number of occurrences exceeds at least onegiven threshold, wherein the life cycle stage is associated with the atleast one given threshold; and notifying a user of the life cycle stateof the flash memory.
 10. The method of claim 9, wherein the at least onelife cycle event comprises at least one of: a write cycle to the flashmemory; a read cycle from the flash memory; a power on cycle of thesecond electronic device; and an error existing in a memory cell of theflash memory.
 11. The method of claim 9, wherein the identifying isbased at least in part on the determining if the total number ofoccurrences exceeds at least one given threshold and the weight assignedto the at least one life cycle.
 12. The method of claim 9, wherein thenotifying further comprises at least one of: visually notifying theuser; and audibly notifying the user.
 13. The method of claim 12,wherein the visually notifying further comprises at least one of:illuminating, at least once, a set of visual indicating means on thesecond electronic device; displaying text on a display of the secondelectronic device; and graphically illustrating on al displaycommunicatively coupled to the first electronic device, a visualnotification associated with the current life cycle stage.
 14. Themethod of claim 9, wherein the current life cycle stage includes atleast one of: a percentage of an estimated life time remaining for theflash memory; an estimated number of remaining life cycle eventsavailable for the flash memory; and an indication of the estimated lifetime remaining for the flash memory being one of: above average,average, and critical.